-
Notifications
You must be signed in to change notification settings - Fork 54
fix(RHOAIENG-25120): remove kueue as mandatory in RayCluster #832
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(RHOAIENG-25120): remove kueue as mandatory in RayCluster #832
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #832 +/- ##
=======================================
Coverage 92.48% 92.48%
=======================================
Files 24 24
Lines 1423 1424 +1
=======================================
+ Hits 1316 1317 +1
Misses 107 107 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
/hold |
The changes look good here @chipspeak would you mind adding verification steps, i'm happy to verify it. :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm!
@kryanbeane: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
VerificationIn a jupyter notebook running on my machine Kueue InstalledInvalid Queue Applying this cluster results in the following error
Valid Queue Creating a Clusterconfig with a local_queue with a value that there IS a. localqueue with that name in the namespace RayCluster is created with the label Kueue Not Installedkueue set to Removed in DSC output is
I was able to clluster.up the resulting raytest cr.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @chipspeak validation went fine. 👍
Just some small suggestions about wording to avoid k8s specific language. also the VAP is being replace so making it more generic will mean we wont need to change the wording going forward
@laurafitzgerald: changing LGTM is restricted to collaborators In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/ok-to-test |
@laurafitzgerald: Cannot trigger testing until a trusted user reviews the PR and leaves an In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Signed-off-by: Pat O'Connor <[email protected]>
859b562
to
d3b58b1
Compare
/ok-to-test |
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kryanbeane, laurafitzgerald The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/override verify-ray_job_client |
@laurafitzgerald: Overrode contexts on behalf of laurafitzgerald: verify-ray_job_client In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
/hold cancel |
/override verify-0_basic_ray verify-1_cluster_job_client verify-2_basic_interactive verify-3_widget_example |
@laurafitzgerald: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
e967fb7
into
project-codeflare:main
Issue link
Jira Link
What changes have been made
Verification steps
Checks